54 |
1Z0-148 |
Which three statements are correct when using collections? (Choose three.) |
|
Associative arrays may be used when you need to process information of unknown volume. |
Nested tables should be used when the index values are non-sequential. |
Use associative arrays when you need numeric and string indices. |
Varrays should be used when you need to pass the collection as a parameter. |
Do not use nested tables when you need to delete elements. |
Nested tables may be used when there is no predefined upper bound for index values. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4, 5, 6 |
|
MC |
|
|
53 |
1Z0-148 |
Examine these two columns: |
53-qplsql.png |
1-c, 2-b, 3-e, 4-a, 5-d |
1-b, 2-d, 3-c, 4-e, 5-a |
1-c, 2-a, 3-b, 4-e, 5-d |
1-c, 2-d, 3-b, 4-e, 5-a |
1-e, 2-a, 3-c, 4-b, 5-d |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4 |
|
SC |
|
|
52 |
1Z0-148 |
Examine this code: |
52-qplsql.png |
First Order Attack |
Second Order Attack |
Incorrect type handling |
Lateral Injection |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2 |
|
SC |
|
|
51 |
1Z0-148 |
You are connected as SCOTT who has an EMP table with this structure: |
51-qplsql.png |
The query will return records pertaining to department 30 with SAL and COMM values displayed as NULL. |
The query will return records pertaining to department 20. |
The query will return records pertaining to department 20 with SAL and COMM values displayed as NULL. |
The query will return records pertaining to department 30. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
|
SC |
|
|
50 |
1Z0-148 |
Which data dictionary view includes information about the parameters of procedures and functions that you can call? |
|
ALL_PROCEDURES |
ALL_PACKAGES |
ALL_ARGUMENTS |
ALL_OBJECTS |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4 |
|
SC |
|
|
49 |
1Z0-148 |
With SERVEROUTPUT enabled, you successfully create the package YEARLY_LIST: |
49-qplsql.png |
Line 6 |
Line 5 |
Line 7 |
Line 2 |
Line 3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3, 5 |
|
MC |
|
|
48 |
1Z0-148 |
Your company’s executive team voted to give a one-time special bonus, the amount of which is to be based on number of years of service. |
|
3 and 4 only |
1, 2, 3, and 4 |
1, 2, and 4 only |
1 and 2 only |
1 and 3 only |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4 |
|
SC |
|
|
47 |
1Z0-148 |
Which statement is true in regard to minimizing attack surface during application design? |
|
Reusable components should be developed and used extensively. |
Only one user account should be used. |
All the code should run anonymously. |
Private functions and procedures should be declared in package specifications. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
|
SC |
|
|
46 |
1Z0-148 |
Examine this PL/SQL block: |
46-qplsql.png |
It fails compilation. |
It executes successfully and outputs "Line: 3". |
It executes successfully and outputs "Line: 5". |
It executes successfully and outputs "Line: ". |
It executes successfully and outputs "Line: 10". |
It executes successfully and outputs "Line: 8". |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
5 |
|
SC |
|
|
45 |
1Z0-148 |
Which two statements are true about conversion from DBMS_SQL to native dynamic SQL? (Choose two.) |
|
The DBMS_SQL.TO_REFCURSOR function should be used when the number of bind variables is known at compile time, but not the number of items to be selected. |
The DBMS_SQL.TO_REFCURSOR function converts a SQL cursor number to a weakly typed cursor variable only after it has been opened, parsed, and executed via DBMS_SQL. |
DBMS_SQL operations can access the cursor only as the SQL cursor number, not as a REF CURSOR variable. |
The DBMS_SQL.TO_REFCURSOR function allows a query result to be returned implicitly from a non PL/SQL environment to a stored PL/SQL program. |
The DBMS_SQL.IS_OPEN function is used to verify that a SQL cursor number is open after it has been converted to a REF CURSOR. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1, 3 |
|
MC |
|
|
44 |
1Z0-148 |
Examine these statements regarding the DBMS_RESULT_CACHE package: |
44-qplsql.png |
2, 3 and 4 |
1 and 4 |
2 and 4 |
1 and 3 |
2 and 3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3 |
|
SC |
|
|
43 |
1Z0-148 |
Which is the correct method for releasing unused money after deleting elements of a collection? |
|
Flush the shared pool using the ALTER SYSTEM command. |
Use the TRUNCATE method on the collection. |
Execute DBMS_SHARED_POOL.UNKEEP. |
Execute DBMS_SESSION.FREE_UNUSED_USER_MEMORY. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4 |
|
SC |
|
|
42 |
1Z0-148 |
Examine the structure of the EMP table: |
42-qplsql.png |
The result cache gets invalidated after the ALTER FUNCTION and again after the second UPDATE statement. |
The result cache gets invalidated after the ALTER FUNCTION and again after each UPDATE statement. |
The result cache gets invalidated only after the ALTER FUNCTION statement. |
The result cache does not get invalidated at all since the RELIES_ON clause is not used. |
The result cache gets invalidated only after each UPDATE statement. |
The result cache gets invalidated only after the second UPDATE statement. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4 |
|
SC |
|
|
41 |
1Z0-148 |
Examine the EMP table: |
41-qplsql.png |
l_sql := 'SELECT empno FROM emp WHERE ename = ''' || SYS.DBMS_ASSERT.NOOP (p_ename) || ''''; |
l_sql := 'SELECT empno FROM emp WHERE ename = ' || SYS.DBMS_ASSERT.QUALIFIED_SQL_NAME (p_ename); |
l_sql := 'SELECT empno FROM emp WHERE ename = ' || SYS.DBMS_ASSERT.SIMPLE_SQL_NAME (p_ename); |
l_sql := 'SELECT empno FROM emp WHERE ename = ' || SYS.DBMS_ASSERT.ENQUOTE_LITERAL (p_ename); |
l_sql := 'SELECT empno FROM emp WHERE ename = ''' || SYS.DBMS_ASSERT.QUALIFIED_SQL_NAME (p_ename) || ''''; |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4 |
|
SC |
|
|
40 |
1Z0-148 |
Examine this code: |
40-qplsql.png |
Hello, edition 1.
Hello, edition 2. |
Hello, edition 1. |
Hello, edition 2. |
Hello, edition 2.
Hello, edition 1. |
An exception is raised. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2 |
|
SC |
|
|
39 |
1Z0-148 |
Which two statements will raise an exception? (Choose two.) |
|
SELECT DBMS_ASSERT.SIMPLE_SQL_NAME ('"10_Employees"') FROM dual; |
SELECT DBMS_ASSERT.SIMPLE_SQL_NAME ('Employees@my_dblink') FROM dual; |
SELECT DBMS_ASSERT.SIMPLE_SQL_NAME (' Emp_Dept_information_table ') FROM dual; |
SELECT DBMS_ASSERT.SIMPLE_SQL_NAME ('Employee_Department_information_table') FROM dual; |
SELECT DBMS_ASSERT.SIMPLE_SQL_NAME ('Employees@') FROM dual; |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1, 5 |
|
MC |
|
|
38 |
1Z0-148 |
You are designing and developing a complex database application and implementing fine-grained access control using security policies. Which statement is true with respect to attaching security policies to database objects? |
|
You can use different security policies for SELECT, INSERT, UPDATE, INDEX and DELETE statements. |
You can use only one security policy per database object. |
You implement security policies through database procedures. |
Column-masking policies can be applied to SELECT, INSERT, UPDATE and DELETE statements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4 |
|
SC |
|
|
37 |
1Z0-148 |
Your company decided to update its employee's contact information as a one-time event. |
37-qplsql.png |
2, 1, 3 and 4 |
1, 2, 4 and 3 |
2, 1, 4 and 3 |
1, 2, 3 and 4 |
2, 4, 1 and 3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
5 |
|
SC |
|
|
36 |
1Z0-148 |
Examine this code (all compiled into schema HR): |
36-qplsql.png |
A |
B |
C |
D |
E |
|
|
|
|
|
|
|
|
|
|
36-Aplans.png |
36-Bplans.png |
36-Cplans.png |
36-Dplans.png |
36-Eplans.png |
|
|
|
|
|
|
|
|
|
|
5 |
|
SC |
|
|
35 |
1Z0-148 |
Examine this function body: |
35-qplsql.png |
A |
B |
C |
D |
E |
|
|
|
|
|
|
|
|
|
|
35-Aplans.png |
35-Bplans.png |
35-Cplans.png |
35-Dplans.png |
35-Eplans.png |
|
|
|
|
|
|
|
|
|
|
2, 4 |
|
MC |
|
|
34 |
1Z0-148 |
Which two are correct when migrating BasicFile LOBs to SecureFile LOBs by DBMS_REDEFINITION? (Choose two.) |
|
Online redefinition can be done only at the table level. |
Specify only BasicFiles LOB and SecureFiles LOB column names in parameter col_mapping of DBMS_REDEFINITION.START_REDEF_TABLE. |
Set the database initialization parameter db_securefile to NEVER. |
During migration, specify the NOLOGGING storage parameter for any new SecureFiles LOB columns. |
Online redefinition is the recommended method for migration of BasicFile LOBs to Secure LOBs. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2, 5 |
|
MC |
|
|
33 |
1Z0-148 |
Examine this function call: |
33-qplsql.png |
CUR_VAL must be opened after this line is executed in the PL/SQL block. |
CUR_VAL must be a weakly typed cursor variable. |
CUR_VAL can be either a strongly or weakly typed cursor variable. |
CUR_VAL must be opened before this line is executed in the PL/SQL block. |
The PL/SQL block can continue to use the cursor variable after this line is executed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3, 4 |
|
MC |
|
|
32 |
1Z0-148 |
Examine this code: |
32-qplsql.png |
A |
B |
C |
D |
E |
|
|
|
|
|
|
|
|
|
|
32-Aplans.png |
32-Bplans.png |
32-Cplans.png |
32-Dplans.png |
32-Eplans.png |
|
|
|
|
|
|
|
|
|
|
2, 4 |
|
MC |
|
|
31 |
1Z0-148 |
Examine the EMPLOYEE_IDS table its data: |
31-qplsql.png |
It executes successfully and outputs:
Fetched: 1011, JJONES, 3789
Fetched: 1012, SSMITH, -1 |
Compilation fails saying EMP_TAXID must be declared. |
An exception is thrown at runtime saying EMP_TAXID is not visible. |
It executes successfully and outputs:
Fetched: 1011, JJONES,
Fetched: 1012, SSMITH, |
It executes successfully and outputs:
Fetched: 1011, JJONES, -1
Fetched: 1012, SSMITH, -1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2 |
|
SC |
|
|
30 |
1Z0-148 |
Examine this external function declaration: |
30-qplsql.png |
OCINumber * compareAndSum (OCIExtProcContext *ctx, OCINumber *p1, OCINumber *p2, OCINumber *p3); |
OCINumber compareAndSum (OCIExtProcContext *ctx, OCINumber p1, OCINumber p2, OCINumber *p3); |
int compareAndSum (OCIExtProcContext *ctx, int p1, int p2, OCINumber *p3); |
int compareAndSum (OCIExtProcContext *ctx, int p1, int p2, OCINumber p3); |
int compareAndSum (OCIExtProcContext *ctx, int p1, int p2, int p3); |
int compareAndSum (OCIExtProcContext *ctx, int p1, int p2, int* p3); |
OCINumber compareAndSum (OCIExtProcContext *ctx, OCINumber p1, OCINumber p2, OCINumber p3); |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6 |
|
SC |
|
|
29 |
1Z0-148 |
Which two can be used to find details of parameters for overloaded PL/SQL routines? (Choose two.) |
|
ALL-DEPENDENCIES |
ALL_PROCEDURES |
ALL_DESCRIBE |
ALL_SOURCE |
ALL_ARGUMENTS |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4, 5 |
|
MC |
|
|
28 |
1Z0-148 |
Which two statements are true about PL/SQL APIs for SecureFiles? (Choose two.) |
|
DBMS_LOB can be used to compress SecureFiles columns. |
When using DBMS_DATAPUMP, if SecureFiles LOB data needs to be encrypted then ENCRYPTION=ALL must be specified. |
If a BasicFiles LOB locator is passed to DBMS_LOB.ISSECUREFILE, an exception will be raised. |
An online redefinition of SecureFiles by DBMS_REDEFINIITON can be performed with PDML (Parallel DML). |
DBMS_LOB cannot be used for SecureFiles if the initialization parameter db_securefile is set to NEVER. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2, 3 |
|
MC |
|
|
27 |
1Z0-148 |
You execute this PL/SQL block: |
27-qplsql.png |
It will fail to compile because of errors at lines 11 and 12. |
It will fail to compile because of errors at lines 6 and 12. |
It will fail to compile because of an error at line 7. |
It will compile and execute successfully. |
It will fail to compile because of errors at lines 5 and 6. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2 |
|
SC |
|
|
26 |
1Z0-148 |
Examine the incomplete code: |
26-qplsql.png |
curid := DBMS_SQL.TO_CURSOR_NUMBER (src_cur); |
src_cur := DBMS_SQL.TO_REFCURSOR (curid); |
src_cur= NUMBER; |
curid NUMBER; |
curid SYS_FEFCURSOR; |
src_cur SYS_REFCURSOR; |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2, 4, 6 |
|
MC |
|
|
25 |
1Z0-148 |
This result cache is enabled for the database instance. |
25-qplsql.png |
Add a parameter, fmt, and change the RETURN statement to:
RETURN TO_CHAR (date_hired, fmt); |
Set the RESULT_CACHE_MODE parameter to FORCE. |
Increase the value for the RESULT_CACHE_MAX_SIZE parameter. |
Change the return type of GET_HIRE_DATE to DATE and have each session invoke the TO_CHAR function. |
Set the RESULT_CACHE_MAX_RESULT parameter to 0. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2, 4 |
|
MC |
|
|
24 |
1Z0-148 |
Examine the structure of the EMP table: |
24-qplsql.png |
A |
B |
C |
D |
|
|
|
|
|
|
|
|
|
|
|
24-Aplans.png |
24-Bplans.png |
24-Cplans.png |
24-Dplans.png |
|
|
|
|
|
|
|
|
|
|
|
3 |
|
SC |
|
|
23 |
1Z0-148 |
Examine these program units: |
23-qplsql.png |
A |
B |
C |
D |
E |
|
|
|
|
|
|
|
|
|
|
23-Aplans.png |
23-Bplans.png |
23-Cplans.png |
23-Dplans.png |
23-Eplans.png |
|
|
|
|
|
|
|
|
|
|
2, 4 |
|
MC |
|
|
22 |
1Z0-148 |
You created a PL/SQL function with the RESULT_CACHE clause, which calculates a percentage of total marks for each student by querying the MARKS table. Under which two circumstances will the cache for this function not be used and the function body be executed instead? (Choose two.) |
|
When a user fixes incorrect marks for a student, with an update to the MARKS table, and then executes the function in the same session |
When the amount of memory allocated for the result cache is increased |
When the function is executed in a session frequently with the same parameter value |
When the database administrator disables the result cache during ongoing application patching |
When the maximum amount of server result cache memory that can be used for a single result is set to 0. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4, 5 |
|
MC |
|
|
21 |
1Z0-148 |
Examine this function: |
21-qplsql.png |
A |
B |
C |
D |
|
|
|
|
|
|
|
|
|
|
|
21-Aplans.png |
21-Bplans.png |
21-Cplans.png |
21-Dplans.png |
|
|
|
|
|
|
|
|
|
|
|
2 |
|
SC |
|
|
20 |
1Z0-148 |
Examine this query executed as SYS and its output: |
20-qplsql.png |
The client-side result cache and the server-side result cache are enabled. |
All distinct query results are cached for the duration of a SYS user session. |
Repetitive SQL queries and PL/SQL functions results are cached and automatically used from the cache across all SYS user sessions. |
The result cache exists but which SQL queries are cached depends on the value of the RESULT_CACHE_MODE parameter. |
Repetitive SQL queries executed on permanent non-dictionary objects may have faster response times. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3, 4 |
|
MC |
|
|
19 |
1Z0-148 |
Select a valid reason for using VARRAYS. |
|
When the amount of data to be held in the collection is widely variable. |
As a column in a table when you want to retrieve the collection data for certain rows by ranges of values. |
When you want to delete elements from the middle of the collection. |
As a column in a table when you want to store no more than 10 elements in each row’s collection. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2 |
|
SC |
|
|
18 |
1Z0-148 |
A PRODUCTS table exists with a PROD_ID column. |
18-qplsql.png |
It executes successfully only if v_ref_cur := DBMS_SQL.TO_REFCURSOR (v_cur); is added before the FETCH statement. |
It executes successfully. |
It executes successfully only if v_ref_cur := DBMS_SQL.TO_CURSOR_NUMBER (v_cur); is added before the FETCH statement. |
It executes successfully only if the FETCH statement is replaced by DBMS_SQL.RETURN_RESULT (v_ref_cur); |
It executes successfully only if the FETCH statement is replaced by DBMS_SQL.FETCH_ROWS (v_cur); |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4 |
|
SC |
|
|
17 |
1Z0-148 |
Examine this code: |
17-qplsql.png |
Define v2 as employees%ROWTYPE. |
Initialize v1 and v2 with appropriate constructor functions. |
Define v2 as pkg. rec. |
Nothing because using the function TABLE (V1) is prohibited. |
Define v1 as employees%ROWTYPE. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1, 3 |
|
MC |
|
|
16 |
1Z0-148 |
Examine this declaration section: |
16-qplsql.png |
A |
B |
C |
D |
E |
|
|
|
|
|
|
|
|
|
|
16-Aplans.png |
16-Bplans.png |
16-Cplans.png |
16-Dplans.png |
16-Eplans.png |
|
|
|
|
|
|
|
|
|
|
4, 5 |
|
MC |
|
|
15 |
1Z0-148 |
Examine this Java method in class Employee, loaded into the Oracle database: |
15-qplsql.png |
A |
B |
C |
D |
E |
|
|
|
|
|
|
|
|
|
|
15-Aplans.png |
15-Bplans.png |
15-Cplans.png |
15-Dplans.png |
15-Eplans.png |
|
|
|
|
|
|
|
|
|
|
4 |
|
SC |
|
|
14 |
1Z0-148 |
Which two statements about the PL/SQL hierarchical profiler are true? (Choose two.) |
|
Access it using the DBMS_PROFILER package. |
Access it using the DBMS_HPROF package. |
Profiler data is recorded in tables and published in HTML reports. |
It is only accessible after a grant of the CREATE PROFILE privilege. |
It helps you identify subprograms that are causing bottlenecks in application performance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2, 5 |
|
MC |
|
|
13 |
1Z0-148 |
Which statement is true about internal and external LOBs? |
|
An external LOB can be loaded into an internal LOB variable using the DBMS_LOB package. |
A NOEXIST_DIRECTORY exception can be raised when using internal and external LOBs. |
Internal and external LOBs can be written using DBMS_LOB. |
After an exception transfers program control outside a PL/SQL block, all references to open external LOBs are lost. |
When using DBMS_LOB.INSTR for internal and external LOBs, DBMS_LOB.OPEN should be called for each LOB. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
5 |
|
SC |
|
|
12 |
1Z0-148 |
Examine this code: |
12-qplsql.png |
Change the RETURN type to DATE. |
Change AUTHID to CURRENT_USER. |
Use the TO_CHAR function around SYSDATE, that is, 1_date := TO_CHAR (SYSDATE). |
Change the data type of 1_date to DATE. |
Set NLS_DATE_FORMAT to ‘DD-MM-YY’ at the instance level. |
Set the RESULT_CACHE_MODE parameter to FORCE. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1, 2 |
|
MC |
|
|
11 |
1Z0-148 |
Which two blocks of code execute successfully? (Choose two.) |
|
A |
B |
C |
D |
E |
|
|
|
|
|
|
|
|
|
|
11-Aplans.png |
11-Bplans.png |
11-Cplans.png |
11-Dplans.png |
11-Eplans.png |
|
|
|
|
|
|
|
|
|
|
2, 4 |
|
MC |
|
|
10 |
1Z0-148 |
Which two statements are true with respect to fine-grained access control? (Choose two.) |
|
It is implemented by end users. |
It can be used to implement column masking. |
It implements security rules through functions and associates these security rules with tables, views or synonyms. |
Separate policies are required for queries versus INSERT/UPDATE/DELETE statements. |
The DBMS_FGA package is used to set up fine-grained access control. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3, 4 |
|
MC |
|
|
9 |
1Z0-148 |
Which must be true in order to add RESULT_CACHE to a function header and have it compile successfully? |
|
The IN parameters must not include BLOB, CLOB, collection or record data types. |
The function must be created with invoker’s rights or in an anonymous block. |
The function must be declared as a pipelined table function. |
The function must have an OUT or an IN OUT parameter. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
|
SC |
|
|
8 |
1Z0-148 |
Select the correct statement regarding BEQUEATH CURRENT_USER. |
|
If a view references a PL/SQL function then BEQUEATH CURRENT_USER allows the function to execute with DBA privileges, regardless of the invoking user’s privileges. |
The BEQUEATH CURRENT_USER clause allows invoker’s rights functions referenced in a view to execute with the privileges of the invoking user. |
Any view calling a PL/SQL function with BEQUEATH CURRENT_USER in effect will execute with the privileges of the function owner. |
With the BEQUEATH CURRENT_USER clause, a definer’s rights function referenced in a view executes with the privileges of the view owner, not the function owner. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2 |
|
SC |
|
|
7 |
1Z0-148 |
Identify the two correct scenarios where a function can be optimized using the function result cache feature. (Choose two.) |
|
A function which inserts multiple records into a DEPARTMENTS table as part of one-time data setup for an HR application. |
A function which accesses multiple tables and calculates the commission to be given to a sales representative based on the number of products sold by that representative. |
A function which deletes all the records from an EMPLOYEES_AUDIT table based on their LOG_DATE. |
A function which updates the SALARY of all the employees in an EMPLOYEES table by a fixed percentage based on their DESIGNATION. |
A function which calculates the factorial of a given number without accessing any table. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4, 5 |
|
MC |
|
|
6 |
1Z0-148 |
Examine this code: |
06-qplsql.png |
SELECT USERENV (‘ACCOUNT_MGR’) FROM dual; |
SELECT SYS_CONTEXT (‘USERENV’, ‘ACCOUNT_MGR’) FROM dual; |
SELECT SYS_CONTEXT (‘ORDER_CTX’, ‘ACCOUNT_MGR’) FROM dual; |
SELECT SYS_CONTEXT (‘ACCOUNT_MGR’, ‘ORDER_CTX’) FROM dual; |
SELECT USERENV (‘ORDER_CTX’) FROM dual; |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2 |
|
SC |
|
|
5 |
1Z0-148 |
Which two statements describe actions developers can take to make their application less vulnerable to security attacks? (Choose two.) |
|
Include the AUTHID DEFINER clause in stored program units. |
Do not concatenate unchecked user input into dynamically constructed SQL statements. |
Switch from using DBMS_SQL to EXECUTE IMMEDIATE. |
Include the AUTHID CURRENT_USER clause in stored program units. |
Increase the amount of code that is accessible to users by default. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2, 4 |
|
MC |
|
|
4 |
1Z0-148 |
Which codes executes successfully? |
|
A |
B |
C |
D |
|
|
|
|
|
|
|
|
|
|
|
04-Aplans.png |
04-Bplans.png |
04-Cplans.png |
04-Dplans.png |
|
|
|
|
|
|
|
|
|
|
|
2 |
|
SC |
|
|
3 |
1Z0-148 |
Examine this code executed as SYS: |
03-qplsql.png |
The procedure needs to be granted the DYNAMIC_TABLE_ROLE role. |
The EXECUTE IMMEDIATE clause is not supported with roles. |
Privileges granted through roles are never in effect when running definer’s rights procedures. |
The user SPIDER needs to be granted the CREATE TABLE privilege and the procedure needs to be granted the DYNAMIC_TABLE_ROLE. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3 |
|
SC |
|
|
2 |
1Z0-148 |
Which statement is true about the DBMS_PARALLEL_EXECUTE package? |
|
DBMS_PARALLEL_EXECUTE is a SYS-owned package and can be accessed only by a user with DBA privileges. |
To execute chunks in parallel, users must have CREATE JOB system privilege. |
No specific system privileges are required to create or run parallel execution tasks. |
Only DBAs can create or run parallel execution tasks. |
Users with CREATE TASK privilege can create or run parallel execution tasks. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2 |
|
SC |
|
|
1 |
1Z0-148 |
The STUDENTS table exists in your schema. |
01-qplsql.png |
A |
B |
C |
D |
E |
|
|
|
|
|
|
|
|
|
|
01-Aplans.png |
01-Bplans.png |
01-Cplans.png |
01-Dplans.png |
01-Eplans.png |
|
|
|
|
|
|
|
|
|
|
1, 5 |
|
MC |
|
|